OCPBUGS-85579: Updates channels to skip v1.19.0 during upgrades - #900
Conversation
openshift-ci-robot
added
jira/severity-important
|
@bharath-b-rh: This pull request references Jira Issue OCPBUGS-85579, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bharath-b-rh The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
Bot
added
the
approved
|
/jira refresh |
openshift-ci-robot
added
jira/valid-bug
|
@bharath-b-rh: This pull request references Jira Issue OCPBUGS-85579, which is valid. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Jira (amendiol@redhat.com), skipping review request. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
Signed-off-by: Bharath B <bhb@redhat.com>
|
/lgtm |
|
@bharath-b-rh: Jira Issue OCPBUGS-85579: All pull requests linked via external trackers have merged:
Jira Issue OCPBUGS-85579 has been moved to the MODIFIED state. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
3 participants
The PR is for updating the channels to skip 1.19.0 which has issue reported in OCPBUGS-85579, where the operator installation fails on console-less cluster. By skipping the operator v1.19.0, users could upgrade from lower versions without any failure directly to v1.19.1.